-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PROJECT_NAME env var to custom run step #578
Conversation
lkysow
commented
Apr 8, 2019
- Fixes [PROPOSAL] Expose project name as environmental variable in run steps #539
- Small refactor of @nikovirtala's work from Expose project name as an environment variable #577
ExpOut string | ||
ExpErr string | ||
Command string | ||
ProjectName string |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nikovirtala what I intended was you add the ProjectName
here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. You give the ProjectName a value inside the cases struct. - That's what I was wondering how to do it. As easy as its part. :)
Codecov Report
@@ Coverage Diff @@
## master #578 +/- ##
==========================================
+ Coverage 72.13% 72.13% +<.01%
==========================================
Files 61 61
Lines 4618 4619 +1
==========================================
+ Hits 3331 3332 +1
Misses 1043 1043
Partials 244 244
Continue to review full report at Codecov.
|
@nikovirtala can you also update https://www.runatlantis.io/docs/custom-workflows.html#custom-run-command |
@lkysow I can update it. Do you want just an addition to the list of variables or with a more complete use case? If latter, I could also include the one how we are using the $WORKSPACE variable to set up workspace specific .tfvars. |
I think just adding it to the list of variables. |